Skip to content

chore(actions): disable scheduled Maven snapshot publishing in fork - #1

Merged
Balerion107 merged 1 commit into
mainfrom
chore/disable-fork-snapshot-publish
Aug 29, 2026
Merged

chore(actions): disable scheduled Maven snapshot publishing in fork#1
Balerion107 merged 1 commit into
mainfrom
chore/disable-fork-snapshot-publish

Conversation

@Balerion107

@Balerion107 Balerion107 commented Aug 29, 2026 •
edited by macroscopeapp Bot
Loading

Copy link
Copy Markdown
Owner

Disables the automatic weekday Maven Central SNAPSHOT publish in this fork while preserving manual workflow_dispatch access.

The scheduled job requires Maven Central credentials/publication ownership that are specific to the upstream project, so automated runs in this fork repeatedly reach the deploy step and fail authentication after building successfully.

Core SDK build and test workflows are unchanged.

Note

Disable scheduled cron trigger in java-publish-snapshot.yml

Removes the weekday 07:00 UTC cron trigger from the Maven snapshot publishing workflow so it no longer runs automatically in this fork. The manual workflow_dispatch trigger is retained.

Macroscope summarized 3fbd20d.

Copilot AI lite review requested due to automatic review settings August 29, 2026 22:01
@qodo-code-review

qodo-code-review Bot commented Aug 29, 2026

Copy link
Copy Markdown

PR Summary by Qodo

Disable scheduled Maven snapshot publishing in fork

⚙️ Configuration changes 🕐 Less than 5 minutes

Grey Divider

AI Description 

• Removes weekday snapshot publishing to prevent credential failures in the fork.
• Preserves manual publishing for explicitly configured fork releases.
• Leaves Java build, validation, and deployment steps unchanged.
High-Level Assessment

Removing only the schedule is the safest approach: it prevents guaranteed fork authentication failures while retaining deliberate manual publishing after credentials and ownership are configured. Adding fork-condition logic was considered unnecessary because this repository intentionally should not publish automatically.

Files changed (1) +4 / -2

Other (1) +4 / -2
java-publish-snapshot.ymlRestrict snapshot publishing to manual dispatch +4/-2

Restrict snapshot publishing to manual dispatch

• Removes the weekday cron trigger while retaining 'workflow_dispatch'. Adds context explaining that upstream-specific Maven Central credentials and publication ownership make automatic fork publishing unsuitable.

.github/workflows/java-publish-snapshot.yml

@Balerion107
Balerion107 merged commit 3b4f67c into main Aug 29, 2026
4 checks passed
@qodo-code-review

qodo-code-review Bot commented Aug 29, 2026

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day 
💡 Did you know, you can group findings by type and pick your Finding display, from Minimal to Full

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Copilot AI reviewed Aug 29, 2026
View reviewed changes

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

Change is narrowly scoped to disabling the scheduled trigger and preserves manual workflow execution as intended.

Pull request overview

Disables the automated scheduled trigger for the Java Maven Central SNAPSHOT publishing workflow in this fork, while keeping manual publishing available via workflow_dispatch, to avoid repeated credential/ownership failures on scheduled runs.

Changes:

  • Removed the weekday schedule (cron) trigger from java-publish-snapshot.yml.
  • Added an in-file comment explaining why scheduled publishing is disabled in the fork and that manual dispatch remains available.
File summaries
File Description
.github/workflows/java-publish-snapshot.yml Removes the cron schedule and documents the fork-specific rationale while retaining manual dispatch.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot
Copilot review effort
Applies to this pull request for everyone.Learn more about Copilot code review.
Copilot left review comments

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Balerion107